Systems and methods for flood area change detection

ABSTRACT

In various embodiments, old flood maps may be compared to new flood maps to determine which areas of the flood map have changed. These changed areas may be correlated against geographic area descriptions that are within changed areas of the flood map. The changed areas may also be analyzed to determine whether each area has had a change in status (e.g., from a high risk flood zone to a non-high risk flood zone or vice versa) or a change in zone within a status (e.g., from one flood zone to another flood zone). The information on type of change (or no change) may be used to populate a database that includes geographic area description identifiers. In some embodiments, detection of certain types of changes may initiate a manual comparison of the old and new flood maps to verify the change.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to flood maps and, morespecifically, to flood area change detection.

2. Description of the Related Art

The National Flood Insurance Reform Act of 1994 extended andreemphasized previous flood insurance acts by requiring federallyregulated lenders not to make, increase, extend, or renew any loan onproperty within a Special Flood Hazard Area (SFHA) unless floodinsurance is purchased. The regulations also require flood insurance atany time during the term of a loan if it is determined that a propertyis within the SFHA. These designations are made and/or modified by theFederal Emergency Management Agency (FEMA). FEMA issues flood maps andflood map revisions on a periodic basis. Zones identified by FEMA onthese maps include: A, AO, A1-A30, AE, AR, AR/AO, AR/A1-A30, AR/AE,AR/AH, AR/A99, A99, AH, VO, V1-V30, VE, V, M, E, X, and D. Zonesbeginning with the letters A or V are considered SFHAs, or high riskflood zones, with A-lettered zones being subject to riverine, lakeoverflow, ponding, or sheetflow flooding and V-lettered zones beingsubject to wave velocity flooding. Zone M designates mudslide proneareas and Zone E designates erosion prone areas. Zones B, C, and Xdesignate areas which are outside of the high risk flood zone, but maystill be subject to a moderate (“500 year” flood zone, or less than 1foot depth in a “100 year” flood zone) (shaded Zone X or Zone B) or low(outside of the “500 year” flood zone) (unshaded Zone X or Zone C) floodrisk. Zone D is used for areas that have not received a flood hazardevaluation, but may be subject to flooding. Zones B, C, X and D zonesare not considered SFHAs.

Because of structural works and improvements, continuing studies, andcorrections/additions, the flood zones for an area may change. FEMA,therefore, periodically issues updated flood maps. These updated mapsmay show that the flood zone classification for some of the areas on themap has changed. For example, some areas that were not in an SFHA maynow be in an SFHA (and vice-versa). Lending companies must stay aware ofthe continuing changes to these flood maps in order to require floodinsurance on applicable properties and to notify borrowers when floodinsurance is no longer required.

SUMMARY OF THE INVENTION

In an embodiment, flood zones on a flood map may be indicated bycomparing two or more flood maps to each other. A first flood map may becompared to an updated second flood map to determine which areas of theflood map have changed between the first flood map and the second floodmap. For example, the first flood map and the updated second flood mapmay be digitized and at least one digitized segment of the first floodmap may be compared to at least one digitized segment of the updatedsecond flood map. Each digitized segment of the first flood map may becompared to the corresponding digitized segment (i.e., the samegeographical area) of the updated second flood map.

One or more areas may be demarcated (e.g., outlined by polygons) on achange map based on the comparison of the first flood map to the updatedsecond flood map. The one or more areas may include at least one area ofa change in status (e.g., from a status as being in a high risk floodzone to a status as a non-high risk flood zone) and at least one area ofa change in zone (e.g., a change of flood zone within the same statusarea, for example, high risk or not). In some embodiments, a street mapmay be digitized to overlay on the change map. The system may determinewhich of the one or more demarcated areas is associated (e.g., overlaps)with at least one geographical area description (e.g., a streetsegment). Street segment data may also be provided, for example, from amap database. In some embodiments, street segments may be definedaccording to a TIGER (Topologically Integrated Geographic Encoding &Referencing system) standard. While several embodiments are describedusing street segments, these embodiments also apply for other geographicarea descriptions for describing locations. For example, instead ofanalyzing which demarcated areas are associated with a street segment,an analysis may include determining which demarcated areas areassociated with specific parcels (e.g., corresponding to geographicboundaries of specific addresses) or specific digital points (or groupsof digital points).

In some embodiments, the one or more demarcated areas associated withthe at least one street segment (or other geographic area description)may be prioritized. For example, a determination may be made whether thestreet segment is associated with at least one area of change in status.The determinations may be made for each street segment on a map. If thestreet segment is associated with at least one area of change in status,the at least one street segment may be assigned an identifier indicatingchange in status. If the street segment is not associated with at leastone area of change in status, a determination may be made as to whetherthe street segment is associated with at least one area of change inzone. If the street segment is associated with at least one area ofchange in zone, the at least one street segment may be assigned anidentifier indicating change in zone. If the street segment is notassociated with at least one area of change in status and is notassociated with at least one area of change in zone, the at least onestreet segment may be assigned an identifier indicating no change. Inone embodiment, the change map may be analyzed to determine if there areother street segments to analyze on the map.

In some embodiments, buffer areas may be placed around demarcated areasand treated as extensions of the areas they are buffering during furtheranalysis. In some embodiments, the size of the buffer may be based onthe accuracy of the flood maps alignment and/or the alignment betweenthe flood maps and a street segment map.

In some embodiments, a manual examination of a geographic areadescription (e.g., a street segment) may be implemented if thegeographic area description is associated with at least one area of achange in zone and/or status. For example, even if only a portion of thestreet segment passes through a change in status area, the entire streetsegment may be manually inspected by a human user.

In some embodiments, at least one database entry for the geographic areadescription (e.g., a street segment) may be updated based on thecomparison. In some embodiments, the database may not designate specificaddresses, but may instead hold information with respect to specificstreet segments. In some embodiments, the database may designate othergeographic area descriptions (e.g., by parcel or group of digitalpoints). The data entries for corresponding street segments in thedatabase may be individually updated with, for example, the statusdetermined for an area through which the street segment passes. In someembodiments, the status may be prioritized (for example, indicator ofchange type=“S” if the street segment passes through a change in statusarea; indicator of a change type=“Z” if the street segment does not passthrough a change in status area but does pass through a change in zonearea; and indicator of a change type=“N” if it passes through neither achange in status area nor a change in zone area.) In some embodiments,the street segments may start with an indicator of change type=“N” andthen updated in a prioritized order. For example, the indicator ofchange type=“Z” may be assigned for the street segments passing througha change in zone area and then the indicator of change type=“S” may beassigned for the street segments passing through a change in statusarea. This ordering may allow change type=“S” identifiers to overwritechange type=“Z” identifiers as appropriate. For example, if a streetsegment is a change type=“S” identifier it may also be a changetype=“Z”. By applying the changes in the above described order, thestreet segments passing even partially through a change in status areamay receive a final identifier of change type=“S” (which may overwritethe previous applied change type=“Z” identifier). Other priorities arealso possible.

For each address for which information is needed, an identifier may bedetermined for the street segment where the address is located. Forexample, another database may be accessed to determine the identifierfor the street segment for which a specific address is located. Usingthe identifier, information for the street segment may be accessed inthe database and returned.

In some embodiments, at least one database entry that corresponds to aproperty (e.g., designated by address) on at least one of the streetsegments (or other geographic area descriptions) may be updated. Forexample, a link may be determined between addresses listed in a databaseand addresses on a corresponding street segment. The data entries forthe corresponding addresses in the database may be individually updatedwith, for example, the status determined for an area through which thestreet segment passes. Properties may be referenced, for example, byaddresses. In some embodiments, the identifiers may be prioritized (forexample, indicated as change type=“S” if the street segment passesthrough a change in status area; indicated as a change type=“Z” if thestreet segment does not pass through a change in status area but doespass through a change in zone area; and indicated as a change type=“N”if it passes through neither a change in status area nor a change inzone area.) In some embodiments, the street segments may start with adefault identifier of change type=“N”. Then street segments passingthrough a change in zone area may receive an identifier of changetype=“Z”, and then street segments passing through a change in statusarea may receive an identifier of change type=“S” (e.g., to allow changetype=“S” to overwrite a previous change type=“Z”). In some embodiments,at least two database entries which correspond to addresses on the atleast one street segment may be updated. In some embodiments, databaseentries for a range of addresses (e.g., addresses lying on the samestreet segment) may be updated at once. Database entries for other typesof geographic area descriptions may also be updated (e.g., entriesspecific to parcels).

The one or more demarcated areas may be displayed with respect to atleast one street segment or other geographic area description. In someembodiments, the demarcated polygons and street segments (or othergeographic area descriptions) may be displayed together (e.g., on acomputer monitor). The user may zoom in on selected specific areas,specific street segments, or specific regions of the map. Otherinteractions between the user and the displayed map are also possible.

In some embodiments, a loan provider, loan recipient, etc. may benotified of a change in status, change in zone, or no change foraddresses on which they request information. For example, electroniccommunications or paper correspondence may be automatically generatedfor one or more addresses, or groups of addresses, which have had achange in status or zone. Loan providers may then require loanrecipients on corresponding addresses to secure flood insurance, secureadditional/less flood insurance, or may notify the recipient that floodinsurance is no longer required.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention may be obtained when thefollowing detailed description is considered in conjunction with thefollowing drawings, in which:

FIG. 1 illustrates an embodiment of a wide area network (“WAN”).

FIG. 2 illustrates an embodiment of computer system that may be suitablefor implementing various embodiments of a system and method for changedetection.

FIGS. 3 a-f illustrate a series of maps showing the union processbetween an old and new flood map, according to an embodiment.

FIGS. 4 a-f illustrates a series of maps and database entries showing aunion process and change detection, according to an embodiment.

FIG. 5 illustrates a change detected map, according to an embodiment.

FIG. 6 illustrates a method for a change detection process, according toan embodiment.

FIGS. 7 a-g illustrate a series of maps used through the changedetection process, according to an embodiment.

FIG. 8 illustrates a method for an old/new zone comparison, according toan embodiment.

FIGS. 9 a-c illustrate a method for a change detection process fordemarcating areas for display, according to an embodiment.

FIG. 10 illustrates another embodiment of a method for assigningidentifiers to geographic area descriptions (e.g., street segments).

FIG. 11 illustrates an embodiment of a method for searching andreplacing identifiers.

FIG. 12 illustrates an embodiment of a method for analyzing addresses inthe demarcated areas.

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and will herein be described in detail. Itshould be understood, however, that the drawings and detaileddescription thereto are not intended to limit the invention to theparticular form disclosed, but on the contrary, the intention is tocover all modifications, equivalents, and alternatives falling withinthe spirit and scope of the present invention as defined by the appendedclaims. Note, the headings are for organizational purposes only and arenot meant to be used to limit or interpret the description or claims.Furthermore, note that the word “may” is used throughout thisapplication in a permissive sense (i.e., having the potential to, beingable to), not a mandatory sense (i.e., must). The term “include”, andderivations thereof, mean “including, but not limited to”. The term“coupled” means “directly or indirectly connected”.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In various embodiments, old flood maps (e.g., FEMA maps) may be comparedto new flood maps to determine which areas of the flood map havechanged. These changed areas may be correlated against a street map (orother map) to identify areas (e.g., parcels, streets, street segmentsand/or other groups of digital points) that are within changed areas ofthe flood map (and parcels, streets, street segments and/or other groupsof digital points that are within unchanged areas of the flood map). Insome embodiments, a Geographic Data Technology, Inc. (GDT) map databasemay be used to provide the street segments or other geographic areadescriptions. Other map databases may also be used. The changed areasmay also be analyzed to determine whether each area has had a change instatus (e.g., from a high risk flood zone to a non-high risk flood zoneor vice versa) or a change in zone within a status (e.g., from one floodzone to a different flood zone). In some embodiments, high risk floodzones may include zones with designations A, A1-A30, A99, AE, AH, AO, V,V1-V30, or VE and non-high risk flood zones may include zones withdesignations B, C, D, X, or X500. In addition, some coastal areas mayreceive designations as coastal areas under CBRA (Coastal BarrierResources Act of 1982 (and/or its amendments)). These areas (which maybe hatched on FEMA maps) are areas in which flood insurance may not beoffered (usually very near the coast). Other zones and zone types arealso possible. The information on the type of change (or no change) maybe used to populate a database that includes geographic areadescriptions (e.g., street segments). In some embodiments, detection ofcertain types of changes may initiate a manual comparison of the old andnew flood maps. For example, street segments with a status change may befurther analyzed to determine the extent of the status change (e.g., todetermine which addresses on the street are included in the statuschange). Street segments with a zone change may also be further analyzed(e.g., to insure the accuracy of the determination and to determinewhich street segments are in the zone change). Companies and/or propertyowners may pay a provider of the service to notify them if an address orgroup of addresses has had a change in status or change in zone becauseof an updated FEMA map. For example, a look-up on each address may beperformed on a database by determining a street segment identifier foreach address and performing a look-up in the database on the informationassociated with that street segment. In some embodiments, information inthe database may be stored by street segment (or other geographic areadescription). In some embodiments, information may be stored on aproperty-by-property basis (e.g., a range of addresses may be updatedaccording to information on their corresponding street segments). Insome embodiments, change detection may be performed on multiple floodmaps (e.g., in a batch process). Change detection between the old mapsand new maps may use computers and databases accessible over wide areanetworks (“WANs”) and/or local area networks (“LANs”).

FIG. 1 illustrates an embodiment of a WAN 102 and a LAN 104. WAN 102 maybe a network that spans a relatively large geographical area. TheInternet is an example of a WAN 102. WAN 102 typically includes aplurality of computer systems that may be interconnected through one ormore networks. Although one particular configuration is shown in FIG. 1,WAN 102 may include a variety of heterogeneous computer systems andnetworks that may be interconnected in a variety of ways and that mayrun a variety of software applications.

One or more LANs 104 may be coupled to WAN 102. LAN 104 may be a networkthat spans a relatively small area. Typically, LAN 104 may be confinedto a single building or group of buildings. Each node (i.e., individualcomputer system or device) on LAN 104 may have its own CPU with which itmay execute programs. Each node may also be able to access data anddevices anywhere on LAN 104. LAN 104, thus, may allow many users toshare devices (e.g., printers) and data stored on file servers. LAN 104may be characterized by a variety of types of topology (i.e., thegeometric arrangement of devices on the network), of protocols (i.e.,the rules and encoding specifications for sending data, and whether thenetwork uses a peer-to-peer or client/server architecture), and of media(e.g., twisted-pair wire, coaxial cables, fiber optic cables, and/orradio waves).

Each LAN 104 may include a plurality of interconnected computer systemsand optionally one or more other devices. For example, LAN 104 mayinclude one or more workstations 110 a, one or more personal computers112 a, one or more laptop or notebook computer systems 114, one or moreserver computer systems 116, and one or more network printers 118. Asillustrated in FIG. 1, an example LAN 104 may include one of eachcomputer systems 110 a, 112 a, 114, and 116, and one printer 118. LAN104 may be coupled to other computer systems and/or other devices and/orother LANs through WAN 102.

One or more mainframe computer systems 120 may be coupled to WAN 102. Asshown, mainframe 120 may be coupled to a storage device or file server124 and mainframe terminals 122 a, 122 b, and 122 c. Mainframe terminals122 a, 122 b, and 122 c may access data stored in the storage device orfile server 124 coupled to or included in mainframe computer system 120.

WAN 102 may also include computer systems connected to WAN 102individually and not through LAN 104. For example, workstation 110 b andpersonal computer 112 b may be connected to WAN 102. For example, WAN102 may include computer systems that may be geographically remote andconnected to each other through the Internet.

FIG. 2 illustrates an embodiment of computer system 250 that may besuitable for implementing various embodiments of a system and method forchange detection. Each computer system 250 typically includes componentssuch as CPU 252 with an associated memory medium such as CD-ROMs 260.The memory medium may store program instructions for computer programs.The program instructions may be executable by CPU 252. Computer system250 may further include a display device such as monitor 254, analphanumeric input device such as keyboard 256, and a directional inputdevice such as mouse 258. Computer system 250 may be operable to executethe computer programs to implement computer-implemented systems andmethods for change detection.

Computer system 250 may include a memory medium on which computerprograms according to various embodiments may be stored. The term“memory medium” is intended to include an installation medium, e.g.,floppy disks or CD-ROMs 260, a computer system memory such as DRAM,SRAM, EDO RAM, Rambus RAM, etc., or a non-volatile memory such as amagnetic media, e.g., a hard drive or optical storage. The memory mediummay also include other types of memory or combinations thereof. Inaddition, the memory medium may be located in a first computer, whichexecutes the programs or may be located in a second different computer,which connects to the first computer over a network. In the latterinstance, the second computer may provide the program instructions tothe first computer for execution. Computer system 250 may take variousforms such as a personal computer system, mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (“PDA”), television system or other device. In general, theterm “computer system” may refer to any device having a processor thatexecutes instructions from a memory medium.

The memory medium may store a software program or programs operable toimplement a method for change detection. The software program(s) may beimplemented in various ways, including, but not limited to,procedure-based techniques, component-based techniques, and/orobject-oriented techniques, among others. For example, the softwareprograms may be implemented using ActiveX controls, C++ objects,JavaBeans, Microsoft Foundation Classes (“MFC”), browser-basedapplications (e.g., Java applets), traditional programs, or othertechnologies or methodologies, as desired. A CPU such as host CPU 252executing code and data from the memory medium may include a means forcreating and executing the software program or programs according to theembodiments described herein.

Various embodiments may also include receiving or storing instructionsand/or data implemented in accordance with the foregoing descriptionupon a carrier medium. Suitable carrier media may include storage mediaor memory media such as magnetic or optical media, e.g., disk or CD-ROM,as well as signals such as electrical, electromagnetic, or digitalsignals, may be conveyed via a communication medium such as a networkand/or a wireless link.

FIG. 3 a illustrates a first map 301 (e.g., an old map) of a high riskflood zone 311 a (e.g., zone=“AE”) and a non-high risk flood zone 313 a(e.g., zone=“X”). FIG. 3 b may illustrate an updated second map 303 withan updated high-risk flood zone 311 b (e.g., zone=“AE”) and non-highrisk flood zone 313 b (e.g., zone=“X”). While several figures describedherein illustrate various maps, as used herein, the term “map” is notrestricted to displayable maps but is also meant to include other datadescriptions including, but not limited to, databases (e.g., informationmay be maintained in a database for digital points in a geographicalarea without necessarily displaying the digital points in a spatialrelationship). In addition, while several embodiments are described withstreet segments, they are also applicable with other geographic areadescriptions (e.g., parcels, groups of digital points, etc.).

The updated high risk flood zone 311 b may have moved with respect tothe old high risk flood zone 311 a shown in FIG. 3 a. The area now inthe non-high risk flood zone 313 b may also have changed (because thehigh risk flood zone 311 b is in a different location). In someembodiments, the first map and/or second map may be digitized (e.g.,points on the map may be assigned attributes such as coordinates,status, zone, etc.). In some embodiments, the digitized map data may beput into a vector data form (e.g., designating the different areas) thatmay then be used by a spatial data engine (e.g., to perform thecomparisons between maps). For example, in some embodiments, ageographical information system (GIS) by Environmental Systems ResearchInstitute (ESRI) may be used to digitize and manage map data during thecomparisons.

FIG. 3 c illustrates a union map 305 of the old high risk flood zone 311a and the new high risk flood zone 311 b (both high risk flood zones)and non-high risk flood zone 313 b. The coordinates of the first map andupdated second map may be aligned for the union. In some embodiments,the first map and second map may have outer boundaries located on thesame coordinates and, therefore, may be aligned according to their outerboundaries. In some embodiments, specific coordinates may be identifiedon each map and aligned with each other during the overlapping of themaps (e.g., the coordinates for a landmark identified on each map may beused to align the maps). In some embodiments, the first map and secondmap may not be actually physically overlapped, but may be digitallyoverlapped (e.g., information on respective coordinates may be kept in adatabase). For example, the maps may be digitized and information aboutdigitized points may be stored (e.g., old status of point, new status ofpoint, geographical coordinates of point, etc.). In some embodiments,points on the map may need to be interpolated (e.g., if a map is to becompared to a map with a higher resolution). In some embodiments, themap data may also be scaled for alignment (e.g., a larger map may bescaled down to be correlated against a smaller map of the same region).

FIG. 3 d illustrates a map 307 showing corresponding areas of change andno-change. Areas on the map may be defined according to areas of change(and/or no change). The boundaries of the overlapping old zones and newzones may be used to demarcate polygons circumscribing the areas ofchange and no change. As used herein, the term “demarcate” refers todefining and/or marking areas (e.g., by outlining in a polygon, usingdifferent types of shading, or using different designators in adatabase). The term “demarcate” as used herein is not meant to berestricted to a displayable element (e.g., a line) but is also meant toinclude, for example, maintaining identifiers in a database fordifferent geographic area descriptions (e.g., a parcel or group ofdigital points on a map). Demarcated areas may include outlined areas(e.g., polygons), geocoded points (e.g., designated withlatitude/longitude), and parcels. Other demarcated areas are alsocontemplated.

In some embodiments, a third flood map may be created which includes oneor more demarcated areas based on the comparisons of the first flood mapand the updated second flood map. In some embodiments, software such asGIS may be used to designate the demarcated polygons. In someembodiments, the areas may be designated by other methods. Thedemarcated areas may receive designators indicating whether the area hashad a change in status, zone, and/or no change. For example, area 351 bmay be within both the old high risk flood zone 311 a and the new highrisk flood zone 311 b. Therefore, area 351 b did not change its statusfrom the first map to the updated second map. In some embodiments, thearea 351 b may receive a designator to indicate that it has not had achange in status. For example, area 351 b may be designated as a nochange in status area (e.g., with a change designator: change type=“N”)to indicate the demarcated area type of area 351 b. Other changedesignators are also contemplated to indicate demarcated area types. Insome embodiments, a specific change designator may not be assigned. Forexample, information for each point on the first map, second map, and/orchange map may be stored and the change type may be determined point bypoint (e.g., for all points or as needed). In some embodiments, insteadof assigning the change designator (or in addition to) other methods ofdesignating the areas are also possible.

As an additional example, area 351 a may have originally been in highrisk flood zone 311 a, but may not be in the new high risk flood zone311 b. Therefore, the status of area 351 a has changed (i.e., from ahigh risk flood zone to a non-high risk flood zone). Area 351 a may bedesignated as a change in status area (e.g., receive a change designatorchange type=“S”) to indicate the demarcated area type of area 351 a.Area 351 c may have not originally been in high risk flood zone 311 a,but may be in high risk flood zone 311 b. Therefore, the status of area351 c has changed (i.e., from a non-high risk flood zone to a high riskflood zone). Area 351 c may be designated as a change in status area(change type=“S”). In addition, area 351 d may be designated as a nochange in status area (e.g., change type=“N”).

FIG. 3 e illustrates a map 308 which illustrates only areas of changetype=“S”. In some embodiments, areas with change type=“N” may not beplaced on third map (and/or may not be displayed). Shaded regions 351 aand 351 c may be shown as part of the third map because they are changetype=“S” areas. In some embodiments, areas of change type=“Z” may alsobe placed on the third map (or optionally not placed on the third map atthe user's discretion).

FIG. 3 f illustrates a map 309 with buffer areas placed around thechange in status areas, according to an embodiment. For example, bufferareas 371 a and 371 b may be placed around change in status areas 351 aand 351 c, respectively. Buffer areas may also be placed around otherareas as well. These buffer areas may be treated as extensions of areasthey are buffering during further analysis (e.g., these area may betreated as change in status areas until a human user manually inspectsthe areas). In some embodiments, the width of the buffer may be based onthe accuracy of the flood maps alignment and/or the alignment betweenthe flood maps and a street segment map. For example, if there is a lotof uncertainty about the alignment, a larger buffer area may be used.Alignment uncertainty may be measured, for example, according to theresolution of the maps (e.g., a finer resolution between the two mapsmay result in a smaller buffer area while, for example, a larger scalemap (with less resolution) may result in a larger buffer area).

FIG. 4 a illustrates a first map 401 of flood zone 411 a (Zone AE),flood zone 421 a (Zone AO), and flood zone 431 a (Zone X). FIG. 4 billustrates an updated second map 403 with a moved and resized floodzone 411 b, flood zone 421 b, and flood zone 431 b. Updated maps mayalso have new zones added and/or old zones removed. Other sources ofzone changes are also possible. FIG. 4 c illustrates a union map 405 ofupdated second map 403 overlaid on first map 401. FIG. 4 d illustrates achange map 407 with corresponding areas of change and no change. Area451 a was in old flood zone 411 a (Zone=AE), but is in the new floodzone 431 b (Zone=X) on the second map. Therefore, area 451 a may bedesignated as a change in status area (change type=“S”) because thechange was from a high-risk flood zone to a non-high risk flood zone.Area 451 b is in the old flood zone 411 a and the updated flood zone 411b and, therefore, may be designated as a no change in status area(change type=“N”) because both the old and new flood zones are high-riskflood zones. Area 451 f was in the old non-high risk flood zone 431 a,but is in the updated high-risk flood zone 411 b and, therefore, may bedesignated as a change in status area (change type=“S”). Area 451 g isin the old non-high risk flood zone 431 a and the updated non-high riskflood zone 431 b (change type=“N”).

Area 451 c is in old flood zone 421 a (zone=AO), but on the updated map,area 451 c is in flood zone 411 b (zone=AE). Because it is in ahigh-risk flood zone in both the old flood map 401 and the updated floodmap 403, it may have the same status. However, because its zone haschanged (from zone AO to zone AE), it may be designated as a change inzone area (change type=“Z”). Area 451 d is in old high-risk flood zone421 a and updated high-risk flood zone 421 b (it may therefore bedesignated change type=“N”). Area 451 e was in old flood zone 411 a, buton the updated map, area 451 e is in flood zone 421 b. Area 451 e,therefore, maintains its status as a high-risk flood zone, but has had azone change (from AE to AO). Area 451 e may be designated a change inzone area (change type=“Z”). Area 451 f may be a change in status area(change type=“S”) and area 451 g may be a no change in status area(change type=“N”).

In some embodiments, a street map (e.g., with geographic areadescriptions such as street segments, parcels, or groups of digitalpoints) may be overlaid on the change map 407. In some embodiments, thestreet map may be digitized to overlay on the change map. In someembodiments, the street map may not be overlaid but may be aligned withthe change map data in a database (or other format). In the embodimentshown in FIG. 4 e, the street segments are shown between “/”s on themap. The street segments may be parsed out of the provided streets ormay be provided in segments from the map database. Other streetsegmenting is also possible. Street segments 471 may be classifiedaccording to the areas they occupy. For example, street segment D 471 dis in area 451 a and therefore may be assigned an indicator of changetype=“S”. Assigning an indicator as used herein refers to generallyindicating a change type and is not meant to be limited to the specificindictors provided herein. For example, other labels, numbers, andqualifiers may also be used to indicate a change type associated with ageographic area description (e.g., displayed map labels or numbersindicative of the change type stored in a database).

As another example, if a street segment passes through a change instatus area (change type=“S”), then the street segment may be assignedan indicator change type=“S” (e.g., street segment C 471 c passesthrough area 451 a (a change type=“S” area) and area 451 g (a changetype=“N” area)). In this example, the change type=“S” may have priorityand, therefore, street segment C 471 c may be assigned an indicatorchange type=“S”. As yet another example, street segment A 471 a passesthrough three areas (451 b, 451 f, and 451 g). Even though two of thethree areas may be change type=“N” areas (451 b and 451 g), the changetype=“S” area (451 f) may prioritize the identifier for street segment A471 a as a change type=“S” area. In some embodiments, other geographicalarea descriptions may be assigned an indicator. For example, a parcel481 may be assigned an indicator change type=“S” because part of theparcel 481 passes through a change type=“S” polygon. As another example,a group of digital points 483 (in an elliptical shape) may also beassigned an indicator change type=“S” because part of the group ofdigital points 483 passes through a change type=“S” polygon. As anotherexample, a geocoded point (e.g., with a specific latitude/longitudedesignation) may also be assigned a change type=“S” or change type=“Z”.

In some embodiments, a street segment in a zone change area may beassigned an indicator of change type=“Z”. For example, street segment E471 e and street segment G 471 g are in areas 451 c and 451 e,respectively (both change in zone areas). Street segment E 471 e andstreet segment G 471 g may, therefore, be assigned an indicator ofchange type=“Z”. Street segment H 471 h crosses through 4 areas (451 b,451 c, 451 d, and 451 e). Areas 451 b and 451 d are designated changetype=“N” areas. Areas 451 c and 451 e are designated change type=“Z”areas. In some embodiments, because the street segment H 471 h crossesthrough a change type=“Z” area (which may have priority over changetype=“N” areas), the street segment may be assigned an indicator changetype=“Z”. Street segment B 471 b and street segment F 471 f may be inchange type=“N” areas (451 g and 451 d, respectively) and, therefore,these street segments may be assigned an indicator change type=“N”.

In some embodiments, street segments (or other geographic areadescriptions) in a change in status area (e.g., with identifiers changetype=“S”) may receive closer scrutiny. For example, these segments maybe manually inspected by a human user. A human user may inspect the oldand/or new flood map to determine if the street segment was properlyassigned the correct indicator. A human user may also analyze the streetsegments to determine which addresses on the street segment should beassigned a change in status indicator. Users may also look at additionaladdresses around designated street segments to determine if otheraddresses should be similarly assigned a change in status indicatorand/or change in zone indicator. Streets with identifiers changetype=“Z” may also receive manual inspection. Street segments withidentifiers change type=“N” may be automatically processed (in someembodiments, they may be manually inspected as well). In someembodiments, street segments with identifiers change type=“S” or changetype=“Z” may also be automatically processed.

As seen in FIG. 4 f, a database 488 (e.g., an Oracle database) ofgeographic area description entries 486 (e.g., street segment entries)may be maintained with database entries for the geographic areadescriptions updated according to the determined change types 484 (adatabase 488 may also be maintained for other geographic areadescriptions, e.g., by parcel). In some embodiments, the database 488may not designate specific addresses, but may instead maintaininformation with respect to specific street segments. In someembodiments, each street segment may have a geographic area descriptionidentifier (e.g., GDT identifier (GDTID) column 482). The data entriesfor the corresponding geographic area descriptions in the database 488may be individually (e.g., according to their GDTID) updated with, forexample, the change type determined for an area through which thegeographic area description passes (e.g., through which the streetsegment passes). In some embodiments, the identifier updates may beprioritized (for example, street segment data updated to indicate changetype=“S” if the street segment passes through a change in status area;indicate a change type=“Z” if the street segment does not pass through achange in status area but does pass through a change in zone area; andindicate a change type=“N” if it passes through neither a change instatus area nor a change in zone area.)

In some embodiments, a range of addresses corresponding to each streetsegment (or geographic area description) may be updated in a database.In some embodiments, the range of addresses (e.g., assigned to aspecific GDTID) may be updated with a new zone identifier (e.g.,zone=AE) and/or a status change identifier (e.g., change type=“S”).Other information may also be updated for the range of addresses. Insome embodiments, instead of updating a database, results of thecomparison may be put into a text document accessible to a user. In someembodiments, the results may be used by other programs.

FIG. 5 illustrates a change detected map (e.g., a third map), accordingto an embodiment. After a map union and zone comparison, a third map maybe generated and displayed indicating different types of changes.Different types of information may be maintained and displayed for thedifferent areas on the map. In some embodiments, Newzone, Oldzone, andchange type variables may be stored and/or displayed for each area(additional information and/or different variable names may also beused). Similar information (or a subset of the information) may also bestored for each street segment or other geographic area description.

In the example shown, area 503 may have been zone X on an old map(Oldzone=X) and may be in a new zone on the new map (Newzone=AE).Because the Oldzone and Newzone have a different status, the change forthe area 503 may be noted as change type=“S”. For example, streetsegment A 511 a may be assigned an indicator of change type=“S” becauseat least part of the segment is within area 503 (with change type=“S”).As another example, area 505 may have been zone AE on an old map(Oldzone=AE) and may be in a new zone on the new map (Newzone=AO).Because the Oldzone and Newzone are different zones within the samestatus, the change for the area 505 may be noted as change type=“Z”.Street segment B 511 b may be assigned an indicator change type=“Z”because at least part of the segment is within area 505 (with changetype=“Z”). In some embodiments, street segments A 511 a and B 511 b mayreceive a manual review (e.g., to determine which parts of the streetsegments are in area 503 and 505, respectively) or may be processedautomatically.

As yet another example, area 507 may have been zone X on an old map(Oldzone=X) and may be in the same zone on the new map (Newzone=X).Because the Oldzone and Newzone are the same, the change for the area507 may be noted as change type=“N”. Street segment C 511 c may beassigned an indicator change type=“N” because the entire segment iswithin area 507 (with change type=“N”). In some embodiments, streetsegment C 511 c may be automatically processed (e.g., a database entryfor addresses on street segment 511 c may be automatically updated toindicate no change in status.)

FIG. 6 illustrates a method for a change detection process, according toan embodiment. It should be noted that in various embodiments of themethods described below, one or more of the elements described may beperformed concurrently, in a different order than shown, or may beomitted entirely. Other additional elements may also be performed asdesired.

At 601, old flood zone data may be received. Old flood zone data mayinclude previous FEMA maps with the locations of previous flood zones.For example, FIG. 7 a illustrates an example of a FEMA map with old zonedata (e.g., for zones 701 a, 703 a, and 705 a). The old flood zone datamay be scanned into the system or received digitally. In someembodiments, the old flood zone data may be received and digitized(e.g., assigning digital values to areas on the maps according to, e.g.,their coordinates and flood zone). FIG. 7 b illustrates an example of adigitized flood zone map with digitized flood zones (e.g., with zonesindicated by designators “V11” 701 b, “B” 703 b, “C” 705 b, etc.). Insome embodiments, each continuous zone on the old FEMA map may bedemarcated in a polygon (with different zones in different polygons).For example, the border between different zones may be a side shared bytwo polygons demarcating the different zones.

At 603, new flood zone data may be received. For example, new flood zonedata may include FEMA maps with the locations of updated flood zones.FIG. 7 c illustrates possible FEMA maps with new flood zone data (e.g.,for zones 707 a, 709 a, and 711 a). The new flood zone data may also bescanned into the system or received digitally. In some embodiments, datamay originate from a FIRM (Flood Insurance Rate Map) or FEMA DFIRM(Digital Flood Insurance Rate Map). These maps may include digital data.Other types of maps and data types are also contemplated. FIG. 7 dillustrates an embodiment of a digitized new flood zone data map (e.g.,with zones indicated by designators “AE” 707 b, “YE” 709 b, “X500” 711b, etc.). In some embodiments, each continuous zone on the new FEMA mapmay be demarcated in a polygon (with different zones in differentpolygons). In some embodiments, the border between different zones maybe a side shared by two polygons demarcating the different zones.

At 605, the new flood data and the old flood data may be unioned. Forexample, the new flood data and old flood data may be digitized andoverlaid on each other. In some embodiments, the data may be coordinatedto align data on one map with corresponding data (e.g., in the sameregion) of the other map. In some embodiments, the maps may not bephysically overlaid, but may have digital data from one region of a mapcoordinated to digital data of the same region on the other map (e.g.,in database form). In some embodiments, data may be scaled and/orinterpolated (e.g., if the digital resolution of one map is less thanthe digital resolution of the map it is being compared to). Thecharacteristics for the new area may be determined based on thecharacteristics of the area in the old map and the new map.

At 607, the old and new zones may be compared. For example, areas of nochange between the maps, change in zone only, and change in status maybe designated by comparing the old and new map zones. An area that hasnot had a change in status or zone (e.g., from zone=X to zone=X) betweenmaps may be separated into a polygon (and designated in a no-changearea). An area that has had a change in zone, but not status, (e.g.,from zone=AE to zone=A0) may be separated into a separate polygon (anddesignated a zone change area). An area that has had a change in status(e.g., from zone=AE to zone=X) may be separated into yet another polygon(and designated a change in status). Polygons may be defined aroundareas of change or no change between the old and new maps. The areas mayalso receive designators (as defined above). The areas may also receivedesignators for zones and/or status on the old map and the new maps(e.g., see FIG. 5).

In some embodiments, old and new zones may be defined according to baseflood elevations (BFEs), other flood elevations lines (e.g., the500-year flood elevation line) and/or the boundaries associated with theBFEs and flood elevation lines. The areas of no change between the maps,change in zone only, and change in status may be designated by comparingthe changes between, for example, BFEs between the first flood map andthe second flood map. For example, the new BFEs on the second flood mapmay indicate that an area of the second flood map is no longer within a100-year flood elevation (as defined by BFEs) and, therefore, the zoneand/or status designation of that area may have changed. In someembodiments, the change may be reflected in a polygon demarcating thechanged area. The change in BFEs and/or other flood elevation lines mayalso be indicated and/or stored relative to the polygon.

At 609, the old and new flood zones may be unioned. In some embodiments,polygons from the old map may be combined with polygons from the newmap. Each area in the combined map bounded by polygon sides may betreated as a new polygon. For example, a new area may be created when anew polygon from the new map cuts through an old polygon from an old mapwhen the two maps are overlaid. New polygons may be created for newregions that do not correspond with an old region (e.g., see FIGS. 3 a-eand FIGS. 4 a-4 d). In some embodiments, the separated polygons may beindicated on a single map (or, for example, in a single database usingdesignators next to corresponding street segments). For example, as seenin FIG. 7 e, a FEMA map with old flood zones and a FEMA map with newflood zones may be digitized and corresponding polygons of the digitizedmaps may be unioned by comparing the zones for each polygon andproviding a new polygon with a designator indicative of the change orlack of change of the corresponding old and new zones. The polygons maybe assigned various values (which may be displayed). For example, asseen in FIG. 7 e, polygon 721 has old zone=“none”, new zone=“VE”, andchange type=“S”. Polygon 723 has old zone=“V11”, new zone=“VE”, andchange type=“Z”. Polygon 725 has old zone=“C”, new zone=“AE”, and changetype=“S”. In some embodiments, only polygons with change type=“S” or “Z”may be displayed. In some embodiments, these polygons may receive amanual inspection.

At 611, street maps/street segments (or other geographic areadescriptions) may be overlaid on the unioned flood zones. For example,GDT streets may be overlaid on the unioned flood zones. As seen in FIG.7 f when the street segments are overlaid or in some other wayassociated with the mapped zones, the street segments (or othergeographic area descriptions) may be assigned indicators according tothe change types of the polygons they cross.

For example, if any part of the street segment crosses a change type=“S”polygon, the street segment may be assigned an indicator change type=“S”(e.g., street segment 751). If the street segment does not cross achange type=“S” polygon, but does cross a change type=“Z” polygon, itmay be assigned an indicator change type=“Z” (e.g., street segment 753).If the street segment does not cross a change type=“S” polygon or achange type=“Z” polygon, but is in a change type=“N” polygon, it may beassigned an indicator change type=“N”.

In some embodiments, each street segment may initially be assigned anindicator change type=“N” and then updated in a prioritized order. Forexample, if part of the street segment (or other geographic areadescription) crosses a change type=“Z” polygon, the street segment maybe assigned an indicator change type=“Z”. Then, if the street segmentcrosses a change type=“S” polygon, the street segment may be assigned anindicator change type=“S”. This ordering may allow change type=“S” tooverwrite change type=“Z” as appropriate. For example, if a streetsegment passes through a change type=“S” polygon, it may have alsopassed through a change type=“Z” polygon. However, the change type=“S”identifier may need to be prioritized over the change type=“Z”identifier (e.g., in order to provide closer analysis to street segmentsthat pass through change type=“S” polygons). In some embodiments, adifferent priority may be used.

In some embodiments, the street segments (or other geographic areadescriptions) may be displayed according to indicator type (e.g., changetype=“S” street segments may be displayed red and change type=“Z” streetsegments and change type=“N” street segments may be displayed green).Other ways of displaying the street segments (or other geographic areadescriptions) are also possible (e.g., using solid lines for changetype=“S” street segments and dashed lines for change type=“Z” or “N”street segments).

At 613, a database may be populated according to street segment (orother geographic area description) identifiers. In some embodiments, thestreet segment identifiers may be populated in a prioritized order. Forexample, the no change identifiers may be populated first. Second, thezone change identifiers may be populated. Finally, the status changeidentifiers may be populated. In this manner, a street segment passingthrough a no change polygon and a status change polygon may be populatedas a no change street segment on a first pass, but then re-designated asa change in status street segment on the third pass. In someembodiments, street segments with change type=“S” may receive a manualinspection prior to being populated to the database. In someembodiments, manual inspections may be done for addresses on a streetsegment=“S” that is looked up in the database. In addition to changetype=“S”, other change types (including “Z” and “N”) may also bemanually inspected.

In some embodiments, addresses that need to be evaluated (e.g., todetermine the current change status for the address or the current floodzone designation for the address) may be indicated on the map (e.g., seestars 771, 773, and 775 in FIG. 7 g). In some embodiments, if there areadditional addresses in a displayed region that need change statusclassification (e.g., through manual inspection), a screen indicator(e.g., screen indicator 777) may be displayed indicating a nearbyaddress. This may allow a user to finish nearby manual inspections. Insome embodiments, the user may classify (e.g., automatically or throughmanual inspection of the change detected flood maps) multiple addressesat the same time. For example, the user may classify addresses 771 and773 as change type=“S” addresses.

While several embodiments are described using street segments, it is tobe understood that these embodiments also apply to using othergeographic area descriptions. For example, instead of analyzing whichdemarcated areas are associated with a street segment, an analysis mayinclude determining which demarcated areas are associated with specificparcels (e.g., corresponding to specific addresses) or specific digitalpoints (or groups of digital points). In some embodiments, instead ofdetermining which change in status areas, change in zone areas, or nochange areas pass through a street segment, a determination may be madeas to which change in status areas, change in zone areas, or no changeareas pass through a parcel or group of data points (and a correspondingindicator of change type=“S”, change type=“Z”, or change type=“N”applied to the geographic area description as described with respect tostreet segment embodiments.)

FIG. 8 illustrates a method for an old/new zone comparison, according toan embodiment. It should be noted that in various embodiments of themethods described below, one or more of the elements described may beperformed concurrently, in a different order than shown, or may beomitted entirely. Other additional elements may also be performed asdesired.

At 801, the unioned old/new zone data may be analyzed. For example, thedata may be compared in a digitized form by a computer system.

At 803, the old zone may be compared to the new zone. In someembodiments, the data may be compared on a point-by-point basis. In someembodiments, the data may be compared on a polygon-by-polygon basis(e.g., a polygon may be an area comprised of points). Other comparisonsare also possible. In some embodiments, other change types may be used.For example, a number (e.g., 0) may be assigned to no change areas and adifferent number assigned to areas of change (e.g., 1).

At 805, if the old zone is the same as the new zone, the portionmatching may be designated change type=“N” (no change).

At 807, if at least a portion of the old zone is not the same as the newzone, the zones may be designated by type. For example, for each oldzone and new zone, a determination may be made as to whether the zone isa high-risk flood zone or a non-high risk flood zone.

At 809, a comparison decision may be made on each zone. For example,overlapping polygons may be compared with each other. At 813, if the oldstatus and the new status of a polygon do not match, the respectivepolygon may be designated with a change type=“S” (or in some other wayindicate that the polygon represents an area in which the status haschanged between the old data and the new data.)

At 815, if the old status and the new status match, but the zones do notmatch, the respective polygon may be designated with a change type=“Z”(or in some other way indicate that the polygon represents an area inwhich the zones have changed between the old data and the new data). Insome embodiments, each polygon may be assigned three values (one for oldzone value, one for new zone value, and one indicating type of change).

FIGS. 9 a-c illustrate a method for a change detection process fordemarcating areas for display, according to an embodiment. It should benoted that in various embodiments of the methods described below, one ormore of the elements described may be performed concurrently, in adifferent order than shown, or may be omitted entirely. Other additionalelements may also be performed as desired.

A first flood map may be compared to an updated second flood map. Forexample, at 903, the first flood map and the updated second flood mapmay be digitized, and at 905, at least one digitized segment of thefirst flood map may be compared to at least one digitized segment of theupdated second flood map. In some embodiments, each digitized segment ofthe first flood map may be compared to the corresponding digitizedsegment of the updated second flood map.

At 907, one or more areas may be demarcated based on the comparison ofthe first flood map to the updated second flood map. At 911, thesedemarcated areas may be indicated/stored on a third flood map. The oneor more areas may comprise one or more areas of a change in statusand/or one or more areas of a change in zone. In some embodiments,demarcating may include demarcating a buffer area around at least onearea. Additionally, one or more geographic area descriptions (e.g.,street segments) may be identified on the comparison map. A streetsegment may be an entire street or a portion of a street.

At 912, a buffer area may be demarcated around at least one of thedemarcated areas.

At 913, a determination may be made whether the street segment (or othergeographic area description) is associated with at least one area ofchange in status. The determinations may be made for the street segmentson the map. At 915, if the street segment is associated with at leastone area of change in status, the street segment may be assigned anidentifier indicating change in status. At 917, if the street segment isnot associated with at least one area of change in status, adetermination may be made whether the street segment is associated withat least one area of change in zone. At 919, if the street segment isassociated with at least one area of change in zone, the street segmentmay be assigned an identifier indicating change in zone. At 921, if thestreet segment is not associated with at least one area of change instatus and is not associated with at least one area of change in zone,the street segment may be assigned an identifier indicating no change.

At 922, the identifier may be stored in a database. For example, as seenin FIG. 4 f, identifier may be stored in the database 488 according tochange type 484 for the geographic area description (e.g., streetsegments).

At 923, a determination may be made whether there is another streetsegment to analyze on the map. At 925, if there is another streetsegment to analyze, the system may proceed to the next street segmentand continue at 913.

At 927, a manual examination of a street segment (or other geographicarea description) may be implemented if the street segment is associatedwith at least one area of a change in status. For example, even if onlya portion of the street segment passes through a change in status area,the entire street segment may be manually inspected by a human user.

At 929, at least one database entry for a street segment (or othergeographic area description) may be updated. In some embodiments, thedatabase may not designate specific addresses, but may instead holdinformation with respect to specific geographic area descriptions (e.g.,street segments). The data entries for the corresponding street segmentsin the database may be individually updated with, for example, thestatus determined for an area through which the street segment passes.In some embodiments, the status may be prioritized. For example, thestreet segment may be indicated as change type=“S” if the street segmentpasses through a change in status area; indicated as a change type=“Z”if the street segment does not pass through a change in status area butdoes pass through a change in zone area; and indicated as a changetype=“N” if it passes through neither a change in status area nor achange in zone area. If the street segment passes through both a changein status area and a change in zone area, the street segment may begiven a change in status identifier, i.e., the change in status may takepriority over a change in zone.

At 930, identifiers stored in the database may be accessed during adatabase look-up. For example, if an identifier is requested for aparticular address (e.g., a user requested address), the address may beaccessed according to a corresponding GDTID for the street segment (orother geographic area description) associated with the address. In someembodiments, addresses associated with the same type of identifier(e.g., addresses associated with a change in status identifier) may besearched in the database automatically and returned to a user forfurther analysis.

At 931, for the addresses that information is needed, a GDTID (or otheridentifier) may be determined for the street segment where the addressis located. For example, another database may be accessed to determinethe identifier for the street segment where a specific address islocated. Other identifiers may also be used (for example, for othergeographic area descriptions).

At 933, using the GDTID (or other identifier) information for the streetsegment (or other geographic area description) may be accessed in thedatabase and returned.

At 935, at least one database entry that corresponds to an address on atleast one of the street segments (or other geographic area descriptions)may be updated. In some embodiments, a link may be determined betweenaddresses listed in a database and addresses on a corresponding streetsegment. The data entries for the corresponding addresses in thedatabase may be individually updated with, for example, the statusdetermined for an area through which the street segment passes.

At 937, at least two database entries which correspond to a range ofaddresses on the at least one street segment (or other geographic areadescription) may be updated. In some embodiments, database entries for arange of addresses (e.g., on the same street segment) may be updated atonce.

At 939, the third flood map (change flood map) and at least one changedesignator (e.g., change type=“S”, change type=“Z”, or change type=“N”)on the third flood map may be displayed. Change designators may indicatea corresponding demarcated area type (e.g., change in status, change inzone, or no change).

At 941, a map of geographic area descriptions (e.g., street segments)may be overlaid on the third flood map (change flood map). In someembodiments, the one or more demarcated areas may be displayed withrespect to at least one street segment (or other geographic areadescription). In some embodiments, the demarcated polygons and streetsegments may be displayed together (e.g., on a computer monitor). Theuser may zoom in on selected specific areas, specific street segments,or specific regions of the map. Other interactions between the user andthe displayed map are also possible. In some embodiments, only changedareas may be displayed to a user (or the changed areas may behighlighted for the user). In some embodiments, obtained maps may bestored in a database and linked together (e.g., by managing designationsfor corresponding regions of the maps).

At 943, a user request may be received for a region of the third floodmap (change flood map) to view and that region may be displayed. In someembodiments, when an identifier for a region (e.g., a regioncorresponding to a zip code) is requested by a user, the maps may beautomatically overlaid such that the information in the requested regionof each of the maps is displayed. In some embodiments, only the userrequested region may be displayed. In some embodiments, the user mayrequest a region by clicking on it or entering a region designator(e.g., a zip code). Other region selection methods are alsocontemplated. In some embodiments, different areas of the maps may bedigitally linked and analyzed as if they were overlapped.

FIG. 10 illustrates another embodiment for assigning identifiers togeographic area descriptions (e.g., street segments). It should be notedthat in various embodiments of the methods described below, one or moreof the elements described may be performed concurrently, in a differentorder than shown, or may be omitted entirely. Other additional elementsmay also be performed as desired.

At 1001, the street segments (or other geographic area descriptions) maybe assigned an identifier indicating no change. In some embodiments, thestreet segments may be given a default identifier of change type=“N”.

At 1003, a determination may be made whether the street segment isassociated with at least one area of change in zone. In someembodiments, the street segments may be analyzed one-by-one. In someembodiments, the street segments may be analyzed in groups.

At 1005, if the street segment is associated with at least one area ofchange in zone, the at least one street segment may be assigned anidentifier indicating change in zone. In some embodiments, the change inzone identifier may overwrite the no change identifier (assigned in1001). Flow may return to 1007.

At 1007, a determination may be made whether the street segment isassociated with at least one area of change in status.

At 1009, if the street segment is associated with at least one area ofchange in status, the at least one street segment may be assigned anidentifier indicating change in status. In some embodiments, the changein status identifier may overwrite the change in zone identifier(assigned in 1005) or the no change identifier (assigned in 1001).

At 1011, a determination may be made whether there is another streetsegment to analyze. At 1013, if there is another street segment toanalyze, the flow may proceed to the next street segment.

As seen in FIG. 10, the street segments (or other geographic areadescriptions) may initially have indicators of change type=“N” assignedto them. The indicators may then be updated in a prioritized order. Forexample, the indicator change type=“Z” may be applied to the streetsegments passing through a change in zone area and then the indicatorchange type=“S” may be applied to the street segments passing through achange in status area. This ordering may allow change type=“S” tooverwrite change type=“Z” as appropriate. For example, if a streetsegment has an indicator change type=“S” it may also be in a changetype=“Z” area. By applying the changes in the above described order, thestreet segments passing even partially through a change in status areamay receive a final identifier of change type=“S” (which may overwrite aprevious indicator change type=“Z”). Other priorities are alsocontemplated.

FIG. 11 illustrates an embodiment of a method for searching and updatingidentifiers. It should be noted that in various embodiments of themethods described below, one or more of the elements described may beperformed concurrently, in a different order than shown, or may beomitted entirely. Other additional elements may also be performed asdesired.

At 1101, demarcated areas that have been designated change in status orchange in zone may be analyzed.

At 1103, a determination may be made as to which geographic areadescriptions (e.g., street segments) cross the demarcated areasdesignated change in status or change in zone.

At 1105, a database may be searched for the entries for the geographicarea descriptions crossing the demarcated areas designated change instatus or change in zone.

At 1107, entries for the geographic area descriptions crossing thedemarcated areas designated change in status or change in zone may beupdated with a change in status or zone identifier in the database (orinitially stored in the database). In some embodiments, geographic areadescriptions with identifiers associated with no change may be ignored(in some embodiments they may also be processed).

At 1109, for the geographic area descriptions with a change in status orzone identifier, a database may be accessed (e.g., searched) foraddresses, parcels, geocoded points, etc. on the geographic areadescription. In some embodiments, the identifiers may be stored with ageographic area description identifier (e.g., a street segmentidentifier) that corresponds to a group of addresses. A separatedatabase (or the same database) may be searched for addressescorresponding to the geographic area descriptions.

At 1111, addresses corresponding to the geographic area descriptioncorresponding to the change in status or zone identifier may bereported. Reporting may include generating a report, sending an email,alerting a loan company, etc. In some embodiments, reports may begenerated for addresses in which a request for status determination wassubmitted by a user (e.g., a loan company). In some embodiments, anidentifier for a requested address may be searched by determining whichgeographic area description corresponds to the address and thendetermining the identifier stored for that geographic area description.The identifier may then be returned for the requested address instead of(or in addition to) reporting the addresses corresponding the geographicarea description with a change in status or zone.

FIG. 12 illustrates an embodiment of a method for analyzing addresses indemarcated areas. It should be noted that in various embodiments of themethods described below, one or more of the elements described may beperformed concurrently, in a different order than shown, or may beomitted entirely. Other additional elements may also be performed asdesired.

At 1201, an address may be examined (e.g., visually) to determine if theaddress is within a demarcated area corresponding to a change in statusor a change in zone.

At 1203, a decision may be made as to whether the address is within ademarcated area corresponding to a change in status or a change in zone.

At 1205, if the address is within a demarcated area corresponding to achange in status or a change in zone, an appropriate identifier for theaddress may be changed in a database, initially stored in a database, orreported according to the status or zone identifier assigned to thecorresponding demarcated area. For example, the previous identifier forthe address may be replaced with the new identifier.

At 1207, if the address does not fall within a demarcated areacorresponding to a change in status or a change in zone, the identifierfor the address may not be changed.

In some embodiments, addresses on a street segment (or other geographicarea description) with a change in status or zone may be manuallyanalyzed and the classification of the addresses may be correspondinglyplaced in the database. In some embodiments, addresses on a streetsegment (or other geographic area description) with a change in statusor zone may be automatically analyzed and the classification of theaddresses may be automatically placed in the database.

In some embodiments, a loan provider, loan recipient, etc. for anaddress may be notified of a change in status or change in zone for thataddress. For example, electronic communications or paper correspondencemay be automatically generated for addresses or groups of addresses thathave had a change in status or zone. In some embodiments, a databaselookup may instead be performed for geographic area descriptions (e.g.,street segments) corresponding to specific addresses. If needed, amanual inspection of the geographic area description (e.g., streetsegment) may be implemented to verify the status of the address.Notified loan providers may then require loan recipients ofcorresponding addresses to secure flood insurance, secureadditional/less flood insurance, or may notify the recipient that floodinsurance is no longer required.

Embodiments of a subset or all (and portions or all) of the above may beimplemented by program instructions stored in a memory medium or carriermedium and executed by a processor. A memory medium may include any ofvarious types of memory devices or storage devices. The term “memorymedium” is intended to include an installation medium, e.g., a CompactDisc Read Only Memory (CD-ROM), floppy disks, or tape device; a computersystem memory or random access memory such as Dynamic Random AccessMemory (DRAM), Double Data Rate Random Access Memory (DDR RAM), StaticRandom Access Memory (SRAM), Extended Data Out Random Access Memory (EDORAM), Rambus Random Access Memory (RAM), etc.; or a non-volatile memorysuch as a magnetic media, e.g., a hard drive, or optical storage. Thememory medium may comprise other types of memory as well, orcombinations thereof. In addition, the memory medium may be located in afirst computer in which the programs are executed, or may be located ina second different computer that connects to the first computer over anetwork, such as the Internet. In the latter instance, the secondcomputer may provide program instructions to the first computer forexecution. The term “memory medium” may include two or more memorymediums that may reside in different locations, e.g., in differentcomputers that are connected over a network.

In some embodiments, a computer system at a respective participantlocation may include a memory medium(s) on which one or more computerprograms or software components according to one embodiment of thepresent invention may be stored. For example, the memory medium maystore one or more programs that are executable to perform the methodsdescribed herein. The memory medium may also store operating systemsoftware, as well as other software for operation of the computersystem.

Further modifications and alternative embodiments of various aspects ofthe invention may be apparent to those skilled in the art in view ofthis description. Accordingly, this description is to be construed asillustrative only and is for the purpose of teaching those skilled inthe art the general manner of carrying out the invention. It is to beunderstood that the forms of the invention shown and described hereinare to be taken as embodiments. Elements and materials may besubstituted for those illustrated and described herein, parts andprocesses may be reversed, and certain features of the invention may beutilized independently, all as would be apparent to one skilled in theart after having the benefit of this description of the invention.Changes may be made in the elements described herein without departingfrom the spirit and scope of the invention as described in the followingclaims.

What is claimed is:
 1. A method, comprising: comparing, by a processor afirst flood map to an updated second flood map, said first flood map andsaid updated second flood map each including flood zones and non-floodzones; and creating, by a processor a third flood map, wherein the thirdflood map includes one or more demarcated areas based on the comparisonof the first flood map to the updated second flood map, and wherein theone or more demarcated marking areas comprises a change designatorindicating a change in risk level status of the first flood map to theupdated second flood map and another designator indicating a change inzone of at least one area from the first flood map to the updated secondflood map, wherein both designators are derived from the comparison ofthe first flood map to the updated second flood map.
 2. The method ofclaim 1, wherein the one or more demarcated areas comprise at least onearea of no change.
 3. The method of claim 1, wherein the one or moredemarcated areas comprise at least one area of a change in risk levelstatus designation and at least one area of a change in zone designationthat is not a change in risk level status designation.
 4. The method ofclaim 1, further comprising demarcating a buffer area around at leastone area of the one or more demarcated areas.
 5. The method of claim 1,further comprising determining which of the one or more demarcated areasis associated with at least one geographic area description.
 6. Themethod of claim 5, wherein the demarcated area is associated with atleast one geographic area description if at least a portion of thegeographic area description crosses through the demarcated area.
 7. Themethod of claim 5, wherein the at least one geographic area descriptionis a street segment.
 8. The method of claim 7, further comprisingprioritizing the one or more demarcated areas associated with the atleast one street segment, wherein prioritizing comprises: assigning theat least one street segment an identifier indicating change in risklevel status designation if the street segment is associated with atleast one demarcated area of the one or mare demarcated areas with achange in risk level status designation; assigning the at least onestreet segment an identifier indicating change in zone if the streetsegment is not associated with at least one demarcated area of the oneor more demarcated areas with the change in risk level statusdesignation and is associated with at least one demarcated area of theone or more demarcated areas with a change in zone designation; andassigning the at least one street segment an identifier indicating nochange if the street segment is not associated with at least onedemarcated area of the one or more demarcated areas with the change inrisk level status designation and is not associated with at least onedemarcated area of the one or more demarcated areas with the change inzone designation.
 9. The method of claim 7, further comprisingprioritizing the one or more demarcated areas associated with the atleast one street segment, wherein prioritizing comprises: assigning theat least one street segment an identifier indicating no change;assigning the at least one street segment an identifier indicatingchange in zone designation if the street segment is associated with atleast one demarcated area of the one or more demarcated areas with achange in zone designation; and assigning the at least one streetsegment an identifier indicating change in risk level status designationif the street segment is associated with at least one demarcated area ofthe one or more demarcated areas with a change in risk level statusdesignation.
 10. The method of claim 1, wherein the first flood map andthe updated second flood map are Flood Insurance Rate Maps (FIRMs). 11.The method of claim 1, wherein one or more demarcated areas comprise atleast one area of a change in zone designation that is not an area of achange in risk level status designation.
 12. The method of claim 1,wherein comparing a first flood map to an updated second flood mapcomprises: digitizing the first flood map and the updated second floodmap; and comparing at least one digitized area of the first flood map toat least one digitized area of the updated second flood map.
 13. Asystem, comprising: a processor; a memory coupled to the processor andconfigured to store program instructions executable by the processor to:compare a first flood map to an updated second flood map, said firstflood map and said updated second flood map each including flood zonesand non-flood zones; and create a third flood map, wherein the thirdflood map includes one or more demarcated areas based on the comparisonof the first flood map to the updated second flood map; wherein the oneor more demarcated marking areas comprises a change designatorindicating a change in risk level status of the first flood map to theupdated second flood map designation and another designator indicating achange in zone of at least one area from the first flood map to theupdated second flood map, wherein both designators are derived from thecomparison of the first flood map to the updated second flood map. 14.The system of claim 13, wherein the one or more demarcated areascomprise at least one area of no change.
 15. The system of claim 13,wherein the one or more demarcated areas comprise at least one area of achange in risk level status designation and at least one area of achange in zone designation that is not a change in risk level statusdesignation.
 16. The system of claim 13, wherein the programinstructions are further executable to demarcate a buffer area around atleast one area of the one or more demarcated areas.
 17. The system ofclaim 13, wherein the program instructions are further executable todetermine which of the one or more demarcated areas is associated withat least one geographic area description.
 18. The system of claim 17,wherein the demarcated area is associated with at least one geographicarea description if at least a portion of the geographic areadescription crosses through the demarcated area.
 19. The system of claim17, wherein the at least one geographic area description is a streetsegment.
 20. The system of claim 19, wherein the program instructionsare further executable to prioritize the one or more demarcated areasassociated with the at least one street segment, wherein prioritizingcomprises: assigning the at least one street segment an identifierindicating change in risk level status designation if the street segmentis associated with at least one demarcated area of the one or moredemarcated areas with a change in risk level status designation;assigning the at least one street segment an identifier indicatingchange in zone designation if the street segment is not associated withat least one demarcated area of the one or more demarcated areas withthe change in risk level status designation and is associated with atleast one demarcated area of the one or more demarcated areas with achange in zone designation; and assigning the at least one streetsegment an identifier indicating no change if the street segment is notassociated with at least one demarcated area of the one or moredemarcated areas with the change in risk level status designation and isnot associated with at least one demarcated area of the one or moredemarcated areas with the change in zone designation.
 21. The system ofclaim 19, wherein the program instructions are further executable toprioritize the one or more demarcated areas associated with the at leastone street segment, wherein prioritizing comprises: assigning the atleast one street segment an identifier indicating no change; assigningthe at least one street segment an identifier indicating change in zonedesignation if the street segment is associated with at least onedemarcated area of the one or more demarcated areas with a change inzone designation; and assigning the at least one street segment anidentifier indicating change in risk level status designation if thestreet segment is associated with at least one demarcated area of theone or more demarcated areas with a change in risk level statusdesignation.
 22. The system of claim 13, wherein the first flood map andthe updated second flood map are Flood Insurance Rate Maps (FIRMs). 23.The system of claim 13, wherein one or more demarcated areas comprise atleast one area of a change in zone designation that is not an area of achange in risk level status designation.
 24. The system of claim 13,wherein comparing a first flood map to an updated second flood mapcomprises: digitizing the first flood map and the updated second floodmap; and comparing at least one digitized area of the first flood map toat least one digitized area of the updated second flood map.
 25. Anon-transitory, computer readable storage medium comprising programinstructions, wherein the program instructions are computer-executableto: compare a first flood map to an updated second flood map, said firstflood map and said updated second flood map each including flood zonesand non-flood zones; and create a third flood map, wherein the thirdflood map includes one or more demarcated areas based on the comparisonof the first flood map to the updated second flood map; wherein the oneor more demarcated marking areas comprises a change designatorindicating a change in risk level status of the first flood map to theupdated second flood map and another designator indicating a change inzone of at least one area from the first flood map to the updated secondflood map, wherein both designators are derived from the comparison ofthe first flood map to the updated second flood map.
 26. Thenon-transitory computer readable medium of claim 25, wherein the one ormore demarcated areas comprise at least one area of no change.
 27. Thenon-transitory computer readable medium of claim 25, wherein the one ormore demarcated areas comprise at least one area of a change in risklevel status designation and at least one area of a change in zonedesignation that is not a change in risk level status designation. 28.The non-transitory computer readable medium of claim 25, wherein theprogram instructions are further executable to demarcate a buffer areaaround at least one area of the one or more demarcated areas.
 29. Thenon-transitory computer readable medium of claim 25, wherein the programinstructions are further executable to determine which of the one ormore demarcated areas is associated with at least one geographic areadescription.
 30. The non-transitory computer readable medium of claim29, wherein the demarcated area is associated with at least onegeographic area description if at least a portion of the geographic areadescription crosses through the demarcated area.
 31. The non-transitorycomputer readable medium of claim 29, wherein the at least onegeographic area description is a street segment.
 32. The non-transitorycomputer readable medium of claim 31, wherein the program instructionsare further executable to prioritize the one or more demarcated areasassociated with the at least one street segment, wherein prioritizingcomprises: assigning the at least one street segment an identifierindicating change in risk level status designation if the street segmentis associated with at least one demarcated area of the one or moredemarcated areas with a change in risk level status designation;assigning the at least one street segment an identifier indicatingchange in zone designation if the street segment is not associated withat least one demarcated area of the one or more demarcated areas withthe change in risk level status designation and is associated with atleast one demarcated area of the one or more demarcated areas with achange in zone designation; and assigning the at least one streetsegment an identifier indicating no change if the street segment is notassociated with at least one demarcated area of the one or moredemarcated areas with the change in risk level status designation and isnot associated with at least one demarcated area of the one or moredemarcated areas with the change in zone designation.
 33. Thenon-transitory computer readable medium of claim 31, wherein the programinstructions are further executable to prioritize the one or moredemarcated areas associated with the at least one street segment,wherein prioritizing comprises: assigning the at least one streetsegment an identifier indicating no change; assigning the at least onestreet segment an identifier indicating change in zone designation ifthe street segment is associated with at least one demarcated area ofthe one or more demarcated areas with a change in zone designation; andassigning the at least one street segment an identifier indicatingchange in risk level status designation if the street segment isassociated with at least one demarcated area of the one or moredemarcated areas with a change in risk level status designation.
 34. Thenon-transitory computer readable medium of claim 25, wherein the firstflood map and the updated second flood map are Flood Insurance Rate Maps(FIRMs).
 35. The non-transitory computer readable medium of claim 25,wherein one or more demarcated areas comprise at least one area of achange in zone designation that is not an area of a change in risk levelstatus designation.
 36. The non-transitory computer readable medium ofclaim 25, wherein comparing a first flood map to an updated second floodmap comprises: digitizing the first flood map and the updated secondflood map; and comparing at least one digitized area of the first floodmap to at least one digitized area of the updated second flood map.